Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9366ac7b104fbeb40b1b131ac700eb9d9f03e443e7f636f8143343c81eb1cb18

Tx prefix hash: f1ed50fc0c31bc05a582dfa2a133c14a871a0140fc9d52e9d519b6e35ee80503
Tx public key: 1bd681b11b22c3bc2dd34020d84254d66e00fd2ca100da7ccda4a3ee32fb35c9
Timestamp: 1741045506 Timestamp [UCT]: 2025-03-03 23:45:06 Age [y:d:h:m:s]: 00:261:17:57:03
Block: 1231575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184814 RingCT/type: yes/0
Extra: 011bd681b11b22c3bc2dd34020d84254d66e00fd2ca100da7ccda4a3ee32fb35c9021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 230df25fc4ee51365fc37e8bd5351c73c1da1e94f38fa4c63613ff4e1a1d47fd 0.600000000000 1718482 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": 1231585, "vin": [ { "gen": { "height": 1231575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "230df25fc4ee51365fc37e8bd5351c73c1da1e94f38fa4c63613ff4e1a1d47fd" } } ], "extra": [ 1, 27, 214, 129, 177, 27, 34, 195, 188, 45, 211, 64, 32, 216, 66, 84, 214, 110, 0, 253, 44, 161, 0, 218, 124, 205, 164, 163, 238, 50, 251, 53, 201, 2, 17, 0, 0, 0, 1, 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