Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8e0c0c99e6e64b34e7baf659825b18ec2a2f1ef0b118ff7de8c0d3e41839d6f

Tx prefix hash: 98333cb943adda7efc338bf8794fe52f1811642311c7d6bfa7766d6863ad7a3e
Tx public key: aa770cf7daf85ff9005c83eaff210bc2ca9284e40712a5faacfef981cb38689a
Timestamp: 1644640077 Timestamp [UCT]: 2022-02-12 04:27:57 Age [y:d:h:m:s]: 02:267:12:05:49
Block: 436761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 710442 RingCT/type: yes/0
Extra: 01aa770cf7daf85ff9005c83eaff210bc2ca9284e40712a5faacfef981cb38689a02110000000606faf294000000000000000000

1 output(s) for total of 21.919457286000 dcy

stealth address amount amount idx
00: 35996803b0fb8bd1ccafaaaad072dea92ceff934b1285df8e3f38c9aa501dc5e 21.919457286000 848206 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": 436771, "vin": [ { "gen": { "height": 436761 } } ], "vout": [ { "amount": 21919457286, "target": { "key": "35996803b0fb8bd1ccafaaaad072dea92ceff934b1285df8e3f38c9aa501dc5e" } } ], "extra": [ 1, 170, 119, 12, 247, 218, 248, 95, 249, 0, 92, 131, 234, 255, 33, 11, 194, 202, 146, 132, 228, 7, 18, 165, 250, 172, 254, 249, 129, 203, 56, 104, 154, 2, 17, 0, 0, 0, 6, 6, 250, 242, 148, 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