Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7738491c4bc8fd5f6eb9ecce5f5d7f47ac5118607b54e4b1e8988dd8bc5c70da

Tx prefix hash: 68763a4d305efcd3e1c78fe177722a4dd794e58e2cd7a43fe1a9eabe5d5933a3
Tx public key: dff775aa2c99ae640ab63a0a207892245c21ef4ffc7a239c9aaaaf1e97d3011b
Timestamp: 1710937814 Timestamp [UCT]: 2024-03-20 12:30:14 Age [y:d:h:m:s]: 01:294:05:23:09
Block: 982448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469047 RingCT/type: yes/0
Extra: 01dff775aa2c99ae640ab63a0a207892245c21ef4ffc7a239c9aaaaf1e97d3011b02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25939075a4952cabd2f4b6a9abc747fe23d0657e97161aef0030e1e15ffef6ca 0.600000000000 1442553 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": 982458, "vin": [ { "gen": { "height": 982448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25939075a4952cabd2f4b6a9abc747fe23d0657e97161aef0030e1e15ffef6ca" } } ], "extra": [ 1, 223, 247, 117, 170, 44, 153, 174, 100, 10, 182, 58, 10, 32, 120, 146, 36, 92, 33, 239, 79, 252, 122, 35, 156, 154, 170, 175, 30, 151, 211, 1, 27, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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