Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e783aa73428d4e63beb56a25cf1615de855f35bcea958c0cbdba972b09ec2def

Tx prefix hash: 7a367682991443473000b0186acbdaac329a5bda06a4cbb456039a036cfe90e6
Tx public key: 550657a2cfef679e13baa529f8d4034b6492c8aaf7d051f7027e6f523226d978
Timestamp: 1725703673 Timestamp [UCT]: 2024-09-07 10:07:53 Age [y:d:h:m:s]: 00:190:02:07:30
Block: 1104846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135704 RingCT/type: yes/0
Extra: 01550657a2cfef679e13baa529f8d4034b6492c8aaf7d051f7027e6f523226d978021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79e8120d2455c51ae9e9a3c1b9896810a6b1f460e67b541cf81718fbe0f12fdd 0.600000000000 1582145 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": 1104856, "vin": [ { "gen": { "height": 1104846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79e8120d2455c51ae9e9a3c1b9896810a6b1f460e67b541cf81718fbe0f12fdd" } } ], "extra": [ 1, 85, 6, 87, 162, 207, 239, 103, 158, 19, 186, 165, 41, 248, 212, 3, 75, 100, 146, 200, 170, 247, 208, 81, 247, 2, 126, 111, 82, 50, 38, 217, 120, 2, 17, 0, 0, 0, 7, 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