Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a55004d27d06ff495d0f4f0597f3eb816032a1d045f0e68ef2164e6e19d4c1a

Tx prefix hash: f42b5533c1be9a066cfcbd24d9e84bec8be08ea71c70f52fbfcee61734ec38d2
Tx public key: 638ea3b099d0d77c902995018c5c2c77674b808379663b45f549176abe2b46fa
Timestamp: 1737412505 Timestamp [UCT]: 2025-01-20 22:35:05 Age [y:d:h:m:s]: 00:303:21:39:59
Block: 1201713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214748 RingCT/type: yes/0
Extra: 01638ea3b099d0d77c902995018c5c2c77674b808379663b45f549176abe2b46fa021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49b3870c7218fe4f48053429d7d180525262d6ac281c3084b1323d2e8f6216a9 0.600000000000 1688370 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": 1201723, "vin": [ { "gen": { "height": 1201713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49b3870c7218fe4f48053429d7d180525262d6ac281c3084b1323d2e8f6216a9" } } ], "extra": [ 1, 99, 142, 163, 176, 153, 208, 215, 124, 144, 41, 149, 1, 140, 92, 44, 119, 103, 75, 128, 131, 121, 102, 59, 69, 245, 73, 23, 106, 190, 43, 70, 250, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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