Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47794c3f577b7719d2b91a0162252397d60db354c26c6eab97d9268c54c1be8d

Tx prefix hash: ffbd141a44ff9d55a8a39471e9353fe9f33a058c592d1237991ab6232f72dfb9
Tx public key: 90c7ad484a06d66a4a0aa187c999c65c7bf93b7fc53ded1e501b5ef0f6ca64b6
Timestamp: 1702108744 Timestamp [UCT]: 2023-12-09 07:59:04 Age [y:d:h:m:s]: 01:191:04:43:04
Block: 909222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397740 RingCT/type: yes/0
Extra: 0190c7ad484a06d66a4a0aa187c999c65c7bf93b7fc53ded1e501b5ef0f6ca64b602110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bfe006fa9f0a8378b27da9665f412e4e424255f3e492202cf33cf8f39c13e6d 0.600000000000 1366293 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": 909232, "vin": [ { "gen": { "height": 909222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bfe006fa9f0a8378b27da9665f412e4e424255f3e492202cf33cf8f39c13e6d" } } ], "extra": [ 1, 144, 199, 173, 72, 74, 6, 214, 106, 74, 10, 161, 135, 201, 153, 198, 92, 123, 249, 59, 127, 197, 61, 237, 30, 80, 27, 94, 240, 246, 202, 100, 182, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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