Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e48642ae2d244a54013740c8d6f078533e0b04339b65a6e6cc74c94736808e8f

Tx prefix hash: 326a37f201022ee73f78cdb0f984642897f9fab3c9831efd531514b69d499de7
Tx public key: 2c21cd6146f5c538ad855fa3ecb031556eb8d15ef3454a8d5010dc582cb11042
Timestamp: 1695517509 Timestamp [UCT]: 2023-09-24 01:05:09 Age [y:d:h:m:s]: 01:123:10:22:30
Block: 854778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349471 RingCT/type: yes/0
Extra: 012c21cd6146f5c538ad855fa3ecb031556eb8d15ef3454a8d5010dc582cb1104202110000000133af99f4000000000000000000

1 output(s) for total of 0.903162091000 dcy

stealth address amount amount idx
00: 9aa83870d2eb3473906414bed3fd5736c53443ca2f9deb8f677a57513588e42a 0.903162091000 1308766 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": 854788, "vin": [ { "gen": { "height": 854778 } } ], "vout": [ { "amount": 903162091, "target": { "key": "9aa83870d2eb3473906414bed3fd5736c53443ca2f9deb8f677a57513588e42a" } } ], "extra": [ 1, 44, 33, 205, 97, 70, 245, 197, 56, 173, 133, 95, 163, 236, 176, 49, 85, 110, 184, 209, 94, 243, 69, 74, 141, 80, 16, 220, 88, 44, 177, 16, 66, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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