Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c77920d09c073e5da975a8abd63bf9043fbcda95c926bbbbbab4e334e8cc67d1

Tx prefix hash: 6ec82324cf914c2d4e98f2fc186a9b1ef9747116aa90009d825cf6c196f99dd5
Tx public key: 153385c7f4aed60ce60bd9a7d415f8ad6906d52d07a86c18742220987d88f4c6
Timestamp: 1722552897 Timestamp [UCT]: 2024-08-01 22:54:57 Age [y:d:h:m:s]: 00:242:00:02:13
Block: 1078711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172861 RingCT/type: yes/0
Extra: 01153385c7f4aed60ce60bd9a7d415f8ad6906d52d07a86c18742220987d88f4c6021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0283ceca0a38f72acd821b6ee5c89076933cd8db24ef0b21ef9d0575564e264a 0.600000000000 1551358 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": 1078721, "vin": [ { "gen": { "height": 1078711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0283ceca0a38f72acd821b6ee5c89076933cd8db24ef0b21ef9d0575564e264a" } } ], "extra": [ 1, 21, 51, 133, 199, 244, 174, 214, 12, 230, 11, 217, 167, 212, 21, 248, 173, 105, 6, 213, 45, 7, 168, 108, 24, 116, 34, 32, 152, 125, 136, 244, 198, 2, 17, 0, 0, 0, 2, 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