Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 780096703590b320a893339d41dc47f78f1c3f6ee6841318d403ed846d029f9e

Tx prefix hash: 51d4700285261dea6e8e52ad2c6ccbfc1128355003a2441766bdca4425669d98
Tx public key: fc90668eb3a4d7ca7afe8069a32814bf9d7e83f8d19537633c712f8b24c81cd8
Timestamp: 1733237792 Timestamp [UCT]: 2024-12-03 14:56:32 Age [y:d:h:m:s]: 00:199:04:43:18
Block: 1167203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142050 RingCT/type: yes/0
Extra: 01fc90668eb3a4d7ca7afe8069a32814bf9d7e83f8d19537633c712f8b24c81cd8021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 788f277e9c304215ce7c88dffdf6cd01d2fb957d06cf6b587a17c67fa3e158a8 0.600000000000 1652898 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": 1167213, "vin": [ { "gen": { "height": 1167203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "788f277e9c304215ce7c88dffdf6cd01d2fb957d06cf6b587a17c67fa3e158a8" } } ], "extra": [ 1, 252, 144, 102, 142, 179, 164, 215, 202, 122, 254, 128, 105, 163, 40, 20, 191, 157, 126, 131, 248, 209, 149, 55, 99, 60, 113, 47, 139, 36, 200, 28, 216, 2, 17, 0, 0, 0, 2, 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