Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b743283ec646d5a8328a0fcbcdfea3e01bca95a981d464580af97ea348201fa4

Tx prefix hash: 7ef017d6d3242471cd3e53e7efe8ccedf39ce3c850ed81a6a4dc244b30313cbe
Tx public key: 102cf1a3d43a846a7fbacd0886a844ef77469e6e0130cac8d523b3b2eeceec89
Timestamp: 1725212084 Timestamp [UCT]: 2024-09-01 17:34:44 Age [y:d:h:m:s]: 00:212:13:39:00
Block: 1100770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151756 RingCT/type: yes/0
Extra: 01102cf1a3d43a846a7fbacd0886a844ef77469e6e0130cac8d523b3b2eeceec89021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bb79c3dd38b5500df642258d5f63e771a2d5d727866b37c5b78f841d92452c5 0.600000000000 1576751 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": 1100780, "vin": [ { "gen": { "height": 1100770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bb79c3dd38b5500df642258d5f63e771a2d5d727866b37c5b78f841d92452c5" } } ], "extra": [ 1, 16, 44, 241, 163, 212, 58, 132, 106, 127, 186, 205, 8, 134, 168, 68, 239, 119, 70, 158, 110, 1, 48, 202, 200, 213, 35, 179, 178, 238, 206, 236, 137, 2, 17, 0, 0, 0, 3, 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