Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1fc890eebce20a9f6f8c03efb5cffc73d613e1c3d0a0321b3ca81bda146c1cf

Tx prefix hash: ec2c7162b73f86771a5d1faa80c5dcd28b7e73df726330c2770e1edb7e7aa181
Tx public key: 5588638b9db00b1fe787c08a13506f58c7e329199c923053972c86c05fdd010d
Timestamp: 1637450682 Timestamp [UCT]: 2021-11-20 23:24:42 Age [y:d:h:m:s]: 02:364:10:24:03
Block: 378604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 778425 RingCT/type: yes/0
Extra: 015588638b9db00b1fe787c08a13506f58c7e329199c923053972c86c05fdd010d021100000001e59f5d07000000000000000000

1 output(s) for total of 34.160810387000 dcy

stealth address amount amount idx
00: f327e2389c2a54d2d2491b0358913543f20cb578bc909767b384beb75a30d944 34.160810387000 765564 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": 378614, "vin": [ { "gen": { "height": 378604 } } ], "vout": [ { "amount": 34160810387, "target": { "key": "f327e2389c2a54d2d2491b0358913543f20cb578bc909767b384beb75a30d944" } } ], "extra": [ 1, 85, 136, 99, 139, 157, 176, 11, 31, 231, 135, 192, 138, 19, 80, 111, 88, 199, 227, 41, 25, 156, 146, 48, 83, 151, 44, 134, 192, 95, 221, 1, 13, 2, 17, 0, 0, 0, 1, 229, 159, 93, 7, 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