Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02f4921be2bda1bbcba29c57c05bf0bf31bfa5d4aa44b2de555a7bad9be47a02

Tx prefix hash: 2865b626b11ed853025b54ecd49d81b1f3a09e3e1b7ae748c3902ee26bb58229
Tx public key: f47df80f972f8ed44ac01feabdd65948a31961951e402e1522fbc4f1434e5d34
Timestamp: 1693538840 Timestamp [UCT]: 2023-09-01 03:27:20 Age [y:d:h:m:s]: 01:144:17:11:01
Block: 838357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364737 RingCT/type: yes/0
Extra: 01f47df80f972f8ed44ac01feabdd65948a31961951e402e1522fbc4f1434e5d3402110000003b4b8f5122000000000000000000

1 output(s) for total of 1.023706154000 dcy

stealth address amount amount idx
00: 67b35567ddf4aea575940cb3a5b368fe38b253d96767b3180514f1da0d42573a 1.023706154000 1291085 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": 838367, "vin": [ { "gen": { "height": 838357 } } ], "vout": [ { "amount": 1023706154, "target": { "key": "67b35567ddf4aea575940cb3a5b368fe38b253d96767b3180514f1da0d42573a" } } ], "extra": [ 1, 244, 125, 248, 15, 151, 47, 142, 212, 74, 192, 31, 234, 189, 214, 89, 72, 163, 25, 97, 149, 30, 64, 46, 21, 34, 251, 196, 241, 67, 78, 93, 52, 2, 17, 0, 0, 0, 59, 75, 143, 81, 34, 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