Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 498ffc90fadac12c7544276d014652fbf5b50e9708d077f2dfc2eb80fc6f37b2

Tx prefix hash: 59f7a378cfbd7f53f050e13526f113899efac30f5841b1bba9e987a3c5ce8ad0
Tx public key: dbf6eb4c06fb2a3747dcbfd89c886ab3ffbb4aa41f1067bfe6664cfc46ea8d09
Timestamp: 1717056441 Timestamp [UCT]: 2024-05-30 08:07:21 Age [y:d:h:m:s]: 00:154:11:14:30
Block: 1033154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110560 RingCT/type: yes/0
Extra: 01dbf6eb4c06fb2a3747dcbfd89c886ab3ffbb4aa41f1067bfe6664cfc46ea8d0902110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89c6d4c57971f8e5292364546e6c7097f2cc3f8830c3542999553522e1849a84 0.600000000000 1501615 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": 1033164, "vin": [ { "gen": { "height": 1033154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89c6d4c57971f8e5292364546e6c7097f2cc3f8830c3542999553522e1849a84" } } ], "extra": [ 1, 219, 246, 235, 76, 6, 251, 42, 55, 71, 220, 191, 216, 156, 136, 106, 179, 255, 187, 74, 164, 31, 16, 103, 191, 230, 102, 76, 252, 70, 234, 141, 9, 2, 17, 0, 0, 0, 5, 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