Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6be01def458c08ad4bc6a74aa852968e44b5dcd04a44063f601f711936e19ea3

Tx prefix hash: a665f841b0d6785895dd281b7f5f88a9281fce1c8b34afca5094ffbe7939e259
Tx public key: 47e187f03c89358dd6e69c42526e8b8a51772a5817b5e925645dcc743310c143
Timestamp: 1699130056 Timestamp [UCT]: 2023-11-04 20:34:16 Age [y:d:h:m:s]: 01:163:16:28:36
Block: 884782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377944 RingCT/type: yes/0
Extra: 0147e187f03c89358dd6e69c42526e8b8a51772a5817b5e925645dcc743310c143021100000006faf35c9c000000000000000000

1 output(s) for total of 0.718372914000 dcy

stealth address amount amount idx
00: 4cb1602e6d60bc1ac7c720f38e92af914e3082733c3416c7700242c4bc0a7301 0.718372914000 1340529 of 0

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": 884792, "vin": [ { "gen": { "height": 884782 } } ], "vout": [ { "amount": 718372914, "target": { "key": "4cb1602e6d60bc1ac7c720f38e92af914e3082733c3416c7700242c4bc0a7301" } } ], "extra": [ 1, 71, 225, 135, 240, 60, 137, 53, 141, 214, 230, 156, 66, 82, 110, 139, 138, 81, 119, 42, 88, 23, 181, 233, 37, 100, 93, 204, 116, 51, 16, 193, 67, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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