Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33e5f2f339da9b1cc11fcbbba0e6eaa1088bd3ccd94c05fd1e059f5fcf3c8860

Tx prefix hash: 5bbe31294db2b602d7a5bc5ad05e637ed6c4e9e876c23bf14d6ebafd34e773b0
Tx public key: 0381ae299846dfcfc9dc10260b5ada1e362f94efddfa82474fc5b99ea611320b
Timestamp: 1723918636 Timestamp [UCT]: 2024-08-17 18:17:16 Age [y:d:h:m:s]: 00:099:08:36:35
Block: 1090052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71067 RingCT/type: yes/0
Extra: 010381ae299846dfcfc9dc10260b5ada1e362f94efddfa82474fc5b99ea611320b02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53eda4430aa2ef0f1b1d5a67c3eb1aef5c58df16ee8f3d67d1a06f647c4e91b3 0.600000000000 1564675 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": 1090062, "vin": [ { "gen": { "height": 1090052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53eda4430aa2ef0f1b1d5a67c3eb1aef5c58df16ee8f3d67d1a06f647c4e91b3" } } ], "extra": [ 1, 3, 129, 174, 41, 152, 70, 223, 207, 201, 220, 16, 38, 11, 90, 218, 30, 54, 47, 148, 239, 221, 250, 130, 71, 79, 197, 185, 158, 166, 17, 50, 11, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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