Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3931fadfbce0eb2bdf9291c31bf1e6e6366e36dbbb11861ac5269fdcffe78f0

Tx prefix hash: a463953678ec074421adfabaf1c797b8f72684ab78490383fc08bd8a0b7f484e
Tx public key: 26e0672e86c7b567b50196fed1cd54d51cba5f7f3ea17f22fa77a92147631b90
Timestamp: 1725717451 Timestamp [UCT]: 2024-09-07 13:57:31 Age [y:d:h:m:s]: 00:281:11:27:15
Block: 1104963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200953 RingCT/type: yes/0
Extra: 0126e0672e86c7b567b50196fed1cd54d51cba5f7f3ea17f22fa77a92147631b90021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e545be2f19b907d1285e8dfc45f0af7f66e327c9207583f28aa64b64c1f7604 0.600000000000 1582298 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": 1104973, "vin": [ { "gen": { "height": 1104963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e545be2f19b907d1285e8dfc45f0af7f66e327c9207583f28aa64b64c1f7604" } } ], "extra": [ 1, 38, 224, 103, 46, 134, 199, 181, 103, 181, 1, 150, 254, 209, 205, 84, 213, 28, 186, 95, 127, 62, 161, 127, 34, 250, 119, 169, 33, 71, 99, 27, 144, 2, 17, 0, 0, 0, 2, 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