Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90c4f16e391ba7e7b0d7f7591683893a1841fc9fab702997dcdc55eafff2b2c5

Tx prefix hash: f37ee17c3a5ff3dd752ba4e114870216f48e9f4f79d246253745e49c03d14ac2
Tx public key: 8da6eac1019e7ec5bab868dadafe4e515da9474679fa32ab436bdf6eac98fb6e
Timestamp: 1702145971 Timestamp [UCT]: 2023-12-09 18:19:31 Age [y:d:h:m:s]: 01:082:19:31:42
Block: 909538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320298 RingCT/type: yes/0
Extra: 018da6eac1019e7ec5bab868dadafe4e515da9474679fa32ab436bdf6eac98fb6e02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02719dbe84df303e5e33dbab34905c400da9d99df4c346e17e0ae2fd1f6f1f1f 0.600000000000 1366633 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": 909548, "vin": [ { "gen": { "height": 909538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02719dbe84df303e5e33dbab34905c400da9d99df4c346e17e0ae2fd1f6f1f1f" } } ], "extra": [ 1, 141, 166, 234, 193, 1, 158, 126, 197, 186, 184, 104, 218, 218, 254, 78, 81, 93, 169, 71, 70, 121, 250, 50, 171, 67, 107, 223, 110, 172, 152, 251, 110, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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