Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3876c86a6aa20aa0dda45ef5fe0c75c55f080b0bc8de80476f28228560f710b9

Tx prefix hash: 44872f7a059a420bc2936b0383bf768b83c7dcc8d90b5d6b86988f6614f2f23e
Tx public key: 5717e0da285a1cdd0323419a8c35b4f386685791d8c23fff96964e00aa68ac02
Timestamp: 1765799235 Timestamp [UCT]: 2025-12-15 11:47:15 Age [y:d:h:m:s]: 00:024:02:49:39
Block: 1434114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17283 RingCT/type: yes/0
Extra: 015717e0da285a1cdd0323419a8c35b4f386685791d8c23fff96964e00aa68ac0202110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f5e3bb788e8da7463df8c2932bda876bdba8c6ee1c8faab2edfff7fc90dfa45 0.600000000000 1922903 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": 1434124, "vin": [ { "gen": { "height": 1434114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f5e3bb788e8da7463df8c2932bda876bdba8c6ee1c8faab2edfff7fc90dfa45" } } ], "extra": [ 1, 87, 23, 224, 218, 40, 90, 28, 221, 3, 35, 65, 154, 140, 53, 180, 243, 134, 104, 87, 145, 216, 194, 63, 255, 150, 150, 78, 0, 170, 104, 172, 2, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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