Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f04137243bce08fd1125e665519016139ce8f4656318bff0e5a7e091b77e0ce

Tx prefix hash: 3e894173ce27e80c9332566683868448ea101d7450010c1731e0c7af161807dc
Tx public key: 026ffed1e69388a0b7c05a5b19b0a2386219fb432a15e9ef6ce3af99e85c4897
Timestamp: 1715769254 Timestamp [UCT]: 2024-05-15 10:34:14 Age [y:d:h:m:s]: 00:287:05:39:04
Block: 1022485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205285 RingCT/type: yes/0
Extra: 01026ffed1e69388a0b7c05a5b19b0a2386219fb432a15e9ef6ce3af99e85c489702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75c1a3d658c32eb52f65942b0dca9f93020fa2fcbb30654b2abf4a7dcf866e90 0.600000000000 1487104 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": 1022495, "vin": [ { "gen": { "height": 1022485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75c1a3d658c32eb52f65942b0dca9f93020fa2fcbb30654b2abf4a7dcf866e90" } } ], "extra": [ 1, 2, 111, 254, 209, 230, 147, 136, 160, 183, 192, 90, 91, 25, 176, 162, 56, 98, 25, 251, 67, 42, 21, 233, 239, 108, 227, 175, 153, 232, 92, 72, 151, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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