Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 671b717e84b8262068e2997304133a8360750ad5b16670ab07e92aa1d76594b9

Tx prefix hash: 9c6d64154e05d90987b1f17b6f76b3943ce0b0c7a2f2cf8cfb824ba72a68c58e
Tx public key: 5f7aa5674f990e110a8206644cc7f3e8f86d143dd569fe63b73dd216c1e31e44
Timestamp: 1721716266 Timestamp [UCT]: 2024-07-23 06:31:06 Age [y:d:h:m:s]: 00:169:22:15:28
Block: 1071771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121590 RingCT/type: yes/0
Extra: 015f7aa5674f990e110a8206644cc7f3e8f86d143dd569fe63b73dd216c1e31e44021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd544d9eb6588168e118f46bce0348c2e739db5a6ecbd0449966d8c8cc6a8b8d 0.600000000000 1544122 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": 1071781, "vin": [ { "gen": { "height": 1071771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd544d9eb6588168e118f46bce0348c2e739db5a6ecbd0449966d8c8cc6a8b8d" } } ], "extra": [ 1, 95, 122, 165, 103, 79, 153, 14, 17, 10, 130, 6, 100, 76, 199, 243, 232, 248, 109, 20, 61, 213, 105, 254, 99, 183, 61, 210, 22, 193, 227, 30, 68, 2, 17, 0, 0, 0, 6, 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