Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e49cba96fcd115290e42bd25b5fc67143b194b9a8e2e16449a8680066daf91d

Tx prefix hash: c571fdf07d6f421a1c653f30de1db9bdcd2a605650a0a3fdfe00bd42a4b378df
Tx public key: fa7dfbfad48c08b6ea21ac8d1fdcee8e7eaca6c93c1dfcfcd76d59313a07a801
Timestamp: 1718829459 Timestamp [UCT]: 2024-06-19 20:37:39 Age [y:d:h:m:s]: 00:361:14:48:13
Block: 1047850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258357 RingCT/type: yes/0
Extra: 01fa7dfbfad48c08b6ea21ac8d1fdcee8e7eaca6c93c1dfcfcd76d59313a07a80102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc9df40d0d159043b70590c4859828658ad498c6fc6d6aa8b1d8b04230cb6802 0.600000000000 1517781 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": 1047860, "vin": [ { "gen": { "height": 1047850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc9df40d0d159043b70590c4859828658ad498c6fc6d6aa8b1d8b04230cb6802" } } ], "extra": [ 1, 250, 125, 251, 250, 212, 140, 8, 182, 234, 33, 172, 141, 31, 220, 238, 142, 126, 172, 166, 201, 60, 29, 252, 252, 215, 109, 89, 49, 58, 7, 168, 1, 2, 17, 0, 0, 0, 1, 82, 212, 126, 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