Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b1e0e28e2daa8e3698a7ee65132b4eabff08efc53e057d646efe330b142c6f14

Tx prefix hash: f1958f892209b15501238c0f4965ad8e7220b98b9f955ea66daed4f66e5709c4
Tx public key: 27a7996a74bede4eff97c3e0023c180a0e2e4e06e6989bda6b659600df178128
Timestamp: 1724679482 Timestamp [UCT]: 2024-08-26 13:38:02 Age [y:d:h:m:s]: 00:282:22:23:11
Block: 1096344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202133 RingCT/type: yes/0
Extra: 0127a7996a74bede4eff97c3e0023c180a0e2e4e06e6989bda6b659600df17812802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb074e829ee6e85eb7f7abe953dd52c30c7158aee0e77f7214dc15b770fb0b3b 0.600000000000 1571533 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1096354, "vin": [ { "gen": { "height": 1096344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb074e829ee6e85eb7f7abe953dd52c30c7158aee0e77f7214dc15b770fb0b3b" } } ], "extra": [ 1, 39, 167, 153, 106, 116, 190, 222, 78, 255, 151, 195, 224, 2, 60, 24, 10, 14, 46, 78, 6, 230, 152, 155, 218, 107, 101, 150, 0, 223, 23, 129, 40, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8