Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc007a67f6318570bdb2f102a9c550f3e1a6f833a8d1faa889bfe0a80d59fdce

Tx prefix hash: 865fd3f6c0846f6efc0b89195f89cae22843278905e74cae905904958a6bc2f5
Tx public key: 55d4a12ec3be5c8b0c903ff550579d156e92c748ab96e7639a899d0ee89c9bcc
Timestamp: 1732492837 Timestamp [UCT]: 2024-11-25 00:00:37 Age [y:d:h:m:s]: 00:128:03:04:42
Block: 1161035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91363 RingCT/type: yes/0
Extra: 0155d4a12ec3be5c8b0c903ff550579d156e92c748ab96e7639a899d0ee89c9bcc0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f24d0b22a9b237e23dd694228c48ce766e65f28a370f0bfbfebec7ff46461c0 0.600000000000 1646686 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": 1161045, "vin": [ { "gen": { "height": 1161035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f24d0b22a9b237e23dd694228c48ce766e65f28a370f0bfbfebec7ff46461c0" } } ], "extra": [ 1, 85, 212, 161, 46, 195, 190, 92, 139, 12, 144, 63, 245, 80, 87, 157, 21, 110, 146, 199, 72, 171, 150, 231, 99, 154, 137, 157, 14, 232, 156, 155, 204, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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