Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af94454ba1adb68b79fc092fb138af10f314bab6021270f8d45240407691530a

Tx prefix hash: 1ddc581a1845ca1d87d788f11611567d11e3dc2d7e704e08f3f8899aa7c6961c
Tx public key: 3d465f74e0c18d52d27fed90a3e5c2f9c5c59c1ce3c27a8887c5c83ece74b432
Timestamp: 1726064968 Timestamp [UCT]: 2024-09-11 14:29:28 Age [y:d:h:m:s]: 00:108:03:55:19
Block: 1107835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77347 RingCT/type: yes/0
Extra: 013d465f74e0c18d52d27fed90a3e5c2f9c5c59c1ce3c27a8887c5c83ece74b432021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a77f12a00ea8b994f31a105e8e109ea42fbc7d727e1830e4a7aa7f7c10168f20 0.600000000000 1585518 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": 1107845, "vin": [ { "gen": { "height": 1107835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a77f12a00ea8b994f31a105e8e109ea42fbc7d727e1830e4a7aa7f7c10168f20" } } ], "extra": [ 1, 61, 70, 95, 116, 224, 193, 141, 82, 210, 127, 237, 144, 163, 229, 194, 249, 197, 197, 156, 28, 227, 194, 122, 136, 135, 197, 200, 62, 206, 116, 180, 50, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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