Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e44784a5a7cf9db7b13d873f56de7316a2bd3a7e01a2ec8c37128867425fa380

Tx prefix hash: 33e3fe7d594d94c6f2701eb877047854aa89bb072c8fdd54324d1f9207f2e21c
Tx public key: 710f96c19880a65a4881838596b120eda9e01fd41d9cd1443e4e615d1d94ffbc
Timestamp: 1710797111 Timestamp [UCT]: 2024-03-18 21:25:11 Age [y:d:h:m:s]: 01:029:10:51:36
Block: 981278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282013 RingCT/type: yes/0
Extra: 01710f96c19880a65a4881838596b120eda9e01fd41d9cd1443e4e615d1d94ffbc02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a0d5e95756093c1b801ad0e17628e4171126c0c4044841f0b3ec1a0b43ed6c6 0.600000000000 1441373 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": 981288, "vin": [ { "gen": { "height": 981278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a0d5e95756093c1b801ad0e17628e4171126c0c4044841f0b3ec1a0b43ed6c6" } } ], "extra": [ 1, 113, 15, 150, 193, 152, 128, 166, 90, 72, 129, 131, 133, 150, 177, 32, 237, 169, 224, 31, 212, 29, 156, 209, 68, 62, 78, 97, 93, 29, 148, 255, 188, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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