Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd6fa1894bed2f5b5f1d1f540f64c5bce33f2e88ff4d8b9493988a20ff5b0d15

Tx prefix hash: 29a37bb38fb1dfed60a0cd66314d82feab2c1e7d2ce3d619eb1f7fca16bf192d
Tx public key: 5400d09af370838270d0aaa76e3f5673e31ba65983aa2537a9bc1f8a1832f474
Timestamp: 1682588159 Timestamp [UCT]: 2023-04-27 09:35:59 Age [y:d:h:m:s]: 01:261:01:17:53
Block: 747645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448050 RingCT/type: yes/0
Extra: 015400d09af370838270d0aaa76e3f5673e31ba65983aa2537a9bc1f8a1832f47402110000000333af99f4000000000000000000

1 output(s) for total of 2.045229081000 dcy

stealth address amount amount idx
00: 4c20b9c08e8637ea1dfad2fb7436e4095984af1d3abaecbf985f9456a54d8182 2.045229081000 1195366 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": 747655, "vin": [ { "gen": { "height": 747645 } } ], "vout": [ { "amount": 2045229081, "target": { "key": "4c20b9c08e8637ea1dfad2fb7436e4095984af1d3abaecbf985f9456a54d8182" } } ], "extra": [ 1, 84, 0, 208, 154, 243, 112, 131, 130, 112, 208, 170, 167, 110, 63, 86, 115, 227, 27, 166, 89, 131, 170, 37, 55, 169, 188, 31, 138, 24, 50, 244, 116, 2, 17, 0, 0, 0, 3, 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