Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f58d2b3016a335fd5aeaeb8051d47665be84fe6361a61d50ecd77e432a9160a5

Tx prefix hash: b2ad7bcb42c96034456e9f1a30af66dc47ad30d78070f3b26d8cb2783113c65b
Tx public key: 1b4e2a1a45043b9c085d33fad352cfcee953bb1b1fc9e8423e0af313a8dc8f82
Timestamp: 1725201006 Timestamp [UCT]: 2024-09-01 14:30:06 Age [y:d:h:m:s]: 00:214:11:10:40
Block: 1100677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153116 RingCT/type: yes/0
Extra: 011b4e2a1a45043b9c085d33fad352cfcee953bb1b1fc9e8423e0af313a8dc8f82021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f04160b0cb16222c8b8b3fc95494cf9d63bd5747ff46d594d10d6d96846f536 0.600000000000 1576656 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": 1100687, "vin": [ { "gen": { "height": 1100677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f04160b0cb16222c8b8b3fc95494cf9d63bd5747ff46d594d10d6d96846f536" } } ], "extra": [ 1, 27, 78, 42, 26, 69, 4, 59, 156, 8, 93, 51, 250, 211, 82, 207, 206, 233, 83, 187, 27, 31, 201, 232, 66, 62, 10, 243, 19, 168, 220, 143, 130, 2, 17, 0, 0, 0, 5, 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