Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 476965e1e40d79a79e3d98a18e94cc9446e1b2a6f2f122187b38886fe572f000

Tx prefix hash: d23a65248b4735c61c58cc6e2eb6d8bbc23dff51b06735e83e8ce0a2f4823827
Tx public key: 7fef3214ad25ba2414247283fbee0671f1d8e56a7189753e36e66f2253fc6b4e
Timestamp: 1701387687 Timestamp [UCT]: 2023-11-30 23:41:27 Age [y:d:h:m:s]: 01:146:18:12:30
Block: 903249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366062 RingCT/type: yes/0
Extra: 017fef3214ad25ba2414247283fbee0671f1d8e56a7189753e36e66f2253fc6b4e02110000000be08532b6000000000000000000

1 output(s) for total of 0.623966229000 dcy

stealth address amount amount idx
00: 492068e535b5293835374c39547f0ead8563652c05679763b1c9ec789cc917a8 0.623966229000 1359922 of 0

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": 903259, "vin": [ { "gen": { "height": 903249 } } ], "vout": [ { "amount": 623966229, "target": { "key": "492068e535b5293835374c39547f0ead8563652c05679763b1c9ec789cc917a8" } } ], "extra": [ 1, 127, 239, 50, 20, 173, 37, 186, 36, 20, 36, 114, 131, 251, 238, 6, 113, 241, 216, 229, 106, 113, 137, 117, 62, 54, 230, 111, 34, 83, 252, 107, 78, 2, 17, 0, 0, 0, 11, 224, 133, 50, 182, 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