Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51bd635be69d9f848f6f2ba7adef0fe31f5db7a6c7b7d7af7c7f24bb7363653f

Tx prefix hash: 414a6c40675a306eb743fd9a0208cec3579caa0fb4518617d97de6f0dacbde9d
Tx public key: 2b7feaa43f71e040c7b9c67406847af59b6606570358a5e2697d9c2be8eb6632
Timestamp: 1726206251 Timestamp [UCT]: 2024-09-13 05:44:11 Age [y:d:h:m:s]: 00:202:14:54:43
Block: 1108999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144651 RingCT/type: yes/0
Extra: 012b7feaa43f71e040c7b9c67406847af59b6606570358a5e2697d9c2be8eb6632021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 160526b5905a841e78609eeb2b9c3fa3149df90adb468268b6de6aa651d5f0b9 0.600000000000 1587096 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": 1109009, "vin": [ { "gen": { "height": 1108999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "160526b5905a841e78609eeb2b9c3fa3149df90adb468268b6de6aa651d5f0b9" } } ], "extra": [ 1, 43, 127, 234, 164, 63, 113, 224, 64, 199, 185, 198, 116, 6, 132, 122, 245, 155, 102, 6, 87, 3, 88, 165, 226, 105, 125, 156, 43, 232, 235, 102, 50, 2, 17, 0, 0, 0, 2, 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