Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 637a193cf9b102eff2f3910712c6819ef418f1ab48fae7ddfd005a173cfd50e2

Tx prefix hash: f110bdded98fd317d8834e3a8742c039ee669f04a1e38ac158d3aca6d4b7a8a3
Tx public key: 9f7ea9e9bc5d8b47bb08664b11b9532ef4c704d111e8c12e503b2ecec6026d5c
Timestamp: 1739104082 Timestamp [UCT]: 2025-02-09 12:28:02 Age [y:d:h:m:s]: 00:317:13:28:04
Block: 1215508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224751 RingCT/type: yes/0
Extra: 019f7ea9e9bc5d8b47bb08664b11b9532ef4c704d111e8c12e503b2ecec6026d5c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4f49f42bb2b493d2356e42173ad7f93ad9f5aa671740caead2fcb8a7e6c243d 0.600000000000 1702307 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": 1215518, "vin": [ { "gen": { "height": 1215508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4f49f42bb2b493d2356e42173ad7f93ad9f5aa671740caead2fcb8a7e6c243d" } } ], "extra": [ 1, 159, 126, 169, 233, 188, 93, 139, 71, 187, 8, 102, 75, 17, 185, 83, 46, 244, 199, 4, 209, 17, 232, 193, 46, 80, 59, 46, 206, 198, 2, 109, 92, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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