Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbdcf4e0b427d0eac0e149cc69608ac4ba263a44cbab5c2fc61fa6a557764535

Tx prefix hash: d309c28d58f5f1f2f3bf9960fd1143f06792ef66bf1a2a18c3034383f21f59e1
Tx public key: 96f680746cb05c9c2d10f470f1f80cdd76279cfce13aca03dd094cd32f073343
Timestamp: 1717185870 Timestamp [UCT]: 2024-05-31 20:04:30 Age [y:d:h:m:s]: 00:304:05:30:26
Block: 1034229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217418 RingCT/type: yes/0
Extra: 0196f680746cb05c9c2d10f470f1f80cdd76279cfce13aca03dd094cd32f07334302110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54329a55e59e227ff9c1973613e6e8e5327d98fc447bee861571e5de254b2e9a 0.600000000000 1502722 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": 1034239, "vin": [ { "gen": { "height": 1034229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54329a55e59e227ff9c1973613e6e8e5327d98fc447bee861571e5de254b2e9a" } } ], "extra": [ 1, 150, 246, 128, 116, 108, 176, 92, 156, 45, 16, 244, 112, 241, 248, 12, 221, 118, 39, 156, 252, 225, 58, 202, 3, 221, 9, 76, 211, 47, 7, 51, 67, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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