Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c4a3f351284612484fb336cb51fbc294a1d1e4deedf9dc485a50585644ca69e

Tx prefix hash: 8a06b2873567d70d7b6987ea9c015cf8f3a183d557e6059746905560436c29b5
Tx public key: beab4662040c38835e64b22fa5901b41641582f42bc3b50a9a625b531e1f99cb
Timestamp: 1711949168 Timestamp [UCT]: 2024-04-01 05:26:08 Age [y:d:h:m:s]: 01:000:16:35:15
Block: 990775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261477 RingCT/type: yes/0
Extra: 01beab4662040c38835e64b22fa5901b41641582f42bc3b50a9a625b531e1f99cb0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cba52cd6bb3d705c4b915880c54e0af26e913494e047925e27c4d433f755994e 0.600000000000 1451103 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": 990785, "vin": [ { "gen": { "height": 990775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cba52cd6bb3d705c4b915880c54e0af26e913494e047925e27c4d433f755994e" } } ], "extra": [ 1, 190, 171, 70, 98, 4, 12, 56, 131, 94, 100, 178, 47, 165, 144, 27, 65, 100, 21, 130, 244, 43, 195, 181, 10, 154, 98, 91, 83, 30, 31, 153, 203, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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