Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af9661fa6f2cf2a29a88e4ea875cdd604064f7d985c1e08458222f06648468d1

Tx prefix hash: f113f673503804903e758fce0e2430c52bee7fd93830424ba902fb1f164b477d
Tx public key: 19a3aa6ed81f5e5918dda3a006ef261446d10c9a5b4a7fe1ccbf89f1efba6365
Timestamp: 1729234150 Timestamp [UCT]: 2024-10-18 06:49:10 Age [y:d:h:m:s]: 00:096:13:56:52
Block: 1134114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68983 RingCT/type: yes/0
Extra: 0119a3aa6ed81f5e5918dda3a006ef261446d10c9a5b4a7fe1ccbf89f1efba6365021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8daf611a5f9560eb1816fdb23c26f1e738c669a9656db5b045e35bbd3395400 0.600000000000 1617365 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": 1134124, "vin": [ { "gen": { "height": 1134114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8daf611a5f9560eb1816fdb23c26f1e738c669a9656db5b045e35bbd3395400" } } ], "extra": [ 1, 25, 163, 170, 110, 216, 31, 94, 89, 24, 221, 163, 160, 6, 239, 38, 20, 70, 209, 12, 154, 91, 74, 127, 225, 204, 191, 137, 241, 239, 186, 99, 101, 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