Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 614cb080db56f00a513aae47751f7032065e6a884377988806d8d23f3f9b4750

Tx prefix hash: 4e68b769576160daa5059a5b4d83d4511d2211edebcbf741cc5fc177c41c7e8f
Tx public key: cf886308ed3fae466c05bdf6d8dc033e3827ace551d1c1055e8adbc00edfa56e
Timestamp: 1707883964 Timestamp [UCT]: 2024-02-14 04:12:44 Age [y:d:h:m:s]: 01:053:07:04:55
Block: 957095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299134 RingCT/type: yes/0
Extra: 01cf886308ed3fae466c05bdf6d8dc033e3827ace551d1c1055e8adbc00edfa56e0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72ae24cc4abcb87791d22ce8b92ceb0d02c371cb9407c66c303efbcf2df5a2c0 0.600000000000 1416411 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": 957105, "vin": [ { "gen": { "height": 957095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72ae24cc4abcb87791d22ce8b92ceb0d02c371cb9407c66c303efbcf2df5a2c0" } } ], "extra": [ 1, 207, 136, 99, 8, 237, 63, 174, 70, 108, 5, 189, 246, 216, 220, 3, 62, 56, 39, 172, 229, 81, 209, 193, 5, 94, 138, 219, 192, 14, 223, 165, 110, 2, 17, 0, 0, 0, 5, 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