Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34fc85877bd89a7fbbe87cc1c7a3c4bb470a56e34f20a982477a82fa38a55359

Tx prefix hash: db8c6abf8742509657c7af418c7928aa6990a0f3cda007759883222d4806b1ee
Tx public key: 76e6da2d9947fe8c6ebb5e4324b1c14894fdb4f31fc8048ce1952c939ad4d8a5
Timestamp: 1725173294 Timestamp [UCT]: 2024-09-01 06:48:14 Age [y:d:h:m:s]: 00:214:19:11:00
Block: 1100445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153357 RingCT/type: yes/0
Extra: 0176e6da2d9947fe8c6ebb5e4324b1c14894fdb4f31fc8048ce1952c939ad4d8a5021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e8b5056d49d905f2ba4324b27db33b5259a8c7a6231505430b51fcda57a6e8d 0.600000000000 1576424 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": 1100455, "vin": [ { "gen": { "height": 1100445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e8b5056d49d905f2ba4324b27db33b5259a8c7a6231505430b51fcda57a6e8d" } } ], "extra": [ 1, 118, 230, 218, 45, 153, 71, 254, 140, 110, 187, 94, 67, 36, 177, 193, 72, 148, 253, 180, 243, 31, 200, 4, 140, 225, 149, 44, 147, 154, 212, 216, 165, 2, 17, 0, 0, 0, 4, 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