Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4583c90f7175a1ba3c3a94e6c74b05a2092193ea4f3fbc3ece50eaae7db29f0f

Tx prefix hash: 97b9740bb9d404b4a41d27578216378642a747a0c0c3824c27b41beab32ef792
Tx public key: 2db50e8d09c17d190662c4da8cf9e5f7bae43066e7f73d43df04abfd763cb0cc
Timestamp: 1741804668 Timestamp [UCT]: 2025-03-12 18:37:48 Age [y:d:h:m:s]: 00:292:19:20:39
Block: 1237871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207050 RingCT/type: yes/0
Extra: 012db50e8d09c17d190662c4da8cf9e5f7bae43066e7f73d43df04abfd763cb0cc0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8345bf2f1efb3db58d5efcec12860a2aa44d0082b8a327e3ab88bddd7ffe184 0.600000000000 1724830 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": 1237881, "vin": [ { "gen": { "height": 1237871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8345bf2f1efb3db58d5efcec12860a2aa44d0082b8a327e3ab88bddd7ffe184" } } ], "extra": [ 1, 45, 181, 14, 141, 9, 193, 125, 25, 6, 98, 196, 218, 140, 249, 229, 247, 186, 228, 48, 102, 231, 247, 61, 67, 223, 4, 171, 253, 118, 60, 176, 204, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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