Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b9da480800def955e9786f666787698ae2da9982e66c06bfd59c6fbd789dc38

Tx prefix hash: 2adfa79ac90505bb6430f9a7c90090c28426662b637d5d34b53c5a18fdb51f9c
Tx public key: 4f29d6ac23f634be79e69b4c2b634973ea0a24e1c8e8c13e216c92b40e128838
Timestamp: 1748186788 Timestamp [UCT]: 2025-05-25 15:26:28 Age [y:d:h:m:s]: 00:251:18:57:20
Block: 1290704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177559 RingCT/type: yes/0
Extra: 014f29d6ac23f634be79e69b4c2b634973ea0a24e1c8e8c13e216c92b40e1288380211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 271b7bc5f1e15a850e916aa79a2a97023a26ee5b16bb037932f6b0812a7f13c2 0.600000000000 1778175 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": 1290714, "vin": [ { "gen": { "height": 1290704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "271b7bc5f1e15a850e916aa79a2a97023a26ee5b16bb037932f6b0812a7f13c2" } } ], "extra": [ 1, 79, 41, 214, 172, 35, 246, 52, 190, 121, 230, 155, 76, 43, 99, 73, 115, 234, 10, 36, 225, 200, 232, 193, 62, 33, 108, 146, 180, 14, 18, 136, 56, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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