Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d56d9a877715b428e12b63377d6110514d2404d028291717d7da22bc427c93e6

Tx prefix hash: c065be328b6f9a3ab4da94174b12cfa19a9c0e940a01a0af2f65b31ee8dab831
Tx public key: 478f071fa4fe0cb1a18401380c73530bf3bbb8cd3299f5276cd539f748dacf65
Timestamp: 1698408703 Timestamp [UCT]: 2023-10-27 12:11:43 Age [y:d:h:m:s]: 01:156:00:32:56
Block: 878775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372501 RingCT/type: yes/0
Extra: 01478f071fa4fe0cb1a18401380c73530bf3bbb8cd3299f5276cd539f748dacf65021100000008faf35c9c000000000000000000

1 output(s) for total of 0.752061995000 dcy

stealth address amount amount idx
00: 69155f7da4a0667f6559e3b90a95c51d46d1945174407ffea52150abebdc833a 0.752061995000 1334251 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": 878785, "vin": [ { "gen": { "height": 878775 } } ], "vout": [ { "amount": 752061995, "target": { "key": "69155f7da4a0667f6559e3b90a95c51d46d1945174407ffea52150abebdc833a" } } ], "extra": [ 1, 71, 143, 7, 31, 164, 254, 12, 177, 161, 132, 1, 56, 12, 115, 83, 11, 243, 187, 184, 205, 50, 153, 245, 39, 108, 213, 57, 247, 72, 218, 207, 101, 2, 17, 0, 0, 0, 8, 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