Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6045d11322c6eb3a26bbb794aac023d405a279a9365e2ec84881649e4735a369

Tx prefix hash: 0d3a78b519d5506fa285e1c79cb1d916a2f40e7d1d2168429b452f7d8c23b474
Tx public key: 908ac789e90a0032e3bbccb48f5593b7f84b61aaadb66cc1ad627dcd46f73dd3
Timestamp: 1726873609 Timestamp [UCT]: 2024-09-20 23:06:49 Age [y:d:h:m:s]: 00:111:13:27:16
Block: 1114536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79772 RingCT/type: yes/0
Extra: 01908ac789e90a0032e3bbccb48f5593b7f84b61aaadb66cc1ad627dcd46f73dd3021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: edc9c90241ba22c0dffa06cb0982c3a13d162f3f70e16181a7a53c181ebb87f3 0.600000000000 1594347 of 15

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": 1114546, "vin": [ { "gen": { "height": 1114536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edc9c90241ba22c0dffa06cb0982c3a13d162f3f70e16181a7a53c181ebb87f3" } } ], "extra": [ 1, 144, 138, 199, 137, 233, 10, 0, 50, 227, 187, 204, 180, 143, 85, 147, 183, 248, 75, 97, 170, 173, 182, 108, 193, 173, 98, 125, 205, 70, 247, 61, 211, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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