Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9eef3fdce9f41162b222b4a3c5f9cb31db558fbc03f8f9660f1e36f4dcec9f7

Tx prefix hash: 4fb0669902cca01c3a382c591283a7f18f849d12f877f40e40bbe1f58f5bcf36
Tx public key: ecf79f5ef8e3f86e04db2890a80bec0f19f27354d9efc4be89f6694370e16439
Timestamp: 1583633882 Timestamp [UCT]: 2020-03-08 02:18:02 Age [y:d:h:m:s]: 04:264:23:21:56
Block: 78351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1084155 RingCT/type: yes/0
Extra: 01ecf79f5ef8e3f86e04db2890a80bec0f19f27354d9efc4be89f6694370e16439021100000001e89b4e54000000000000000000

1 output(s) for total of 337.591423080000 dcy

stealth address amount amount idx
00: 390a17fea7a90810ce4a69d3ce97a24c10bf7cf3dcd0b2f642ef5809fdbea263 337.591423080000 143795 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": 78361, "vin": [ { "gen": { "height": 78351 } } ], "vout": [ { "amount": 337591423080, "target": { "key": "390a17fea7a90810ce4a69d3ce97a24c10bf7cf3dcd0b2f642ef5809fdbea263" } } ], "extra": [ 1, 236, 247, 159, 94, 248, 227, 248, 110, 4, 219, 40, 144, 168, 11, 236, 15, 25, 242, 115, 84, 217, 239, 196, 190, 137, 246, 105, 67, 112, 225, 100, 57, 2, 17, 0, 0, 0, 1, 232, 155, 78, 84, 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