Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 406af4d70d9ee43c746e06c2507874ef24a0b2a0b9db89abe574b3963bac75c9

Tx prefix hash: bee3f46c0f98d968114f5e298c91293f440c117602ffd6de6b39c2bd201bbd81
Tx public key: f928570dd0bd8c70dd5946a813e246fe569b7d6aee3373e2e69f7489f61f2b95
Timestamp: 1737129729 Timestamp [UCT]: 2025-01-17 16:02:09 Age [y:d:h:m:s]: 00:156:05:15:14
Block: 1199414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111271 RingCT/type: yes/0
Extra: 01f928570dd0bd8c70dd5946a813e246fe569b7d6aee3373e2e69f7489f61f2b95021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef9a56a4ab85285b6e7ca2d04faaac4fdf5bba18485886de3f5846c124db6608 0.600000000000 1686045 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": 1199424, "vin": [ { "gen": { "height": 1199414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef9a56a4ab85285b6e7ca2d04faaac4fdf5bba18485886de3f5846c124db6608" } } ], "extra": [ 1, 249, 40, 87, 13, 208, 189, 140, 112, 221, 89, 70, 168, 19, 226, 70, 254, 86, 155, 125, 106, 238, 51, 115, 226, 230, 159, 116, 137, 246, 31, 43, 149, 2, 17, 0, 0, 0, 4, 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