Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67a8ba416209d9b01568f76f8e1151c308aeba99656ebc6f4edbcbb416b27fa2

Tx prefix hash: a6b8564aa75d7175dfe1dd5921528a790f2ddbbd3aa6e82a351be69a77c43f11
Tx public key: 61155d8a7a2835066cb1cf3f0fe8fd919037653b842febf7977e3774e239cc36
Timestamp: 1724267834 Timestamp [UCT]: 2024-08-21 19:17:14 Age [y:d:h:m:s]: 01:078:21:03:58
Block: 1092944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314820 RingCT/type: yes/0
Extra: 0161155d8a7a2835066cb1cf3f0fe8fd919037653b842febf7977e3774e239cc36021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b085c51ad9b5f551c272b53d2f2fcdacd8cc1705245ec9a5cf8d53ca1cfc9bb 0.600000000000 1567791 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": 1092954, "vin": [ { "gen": { "height": 1092944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b085c51ad9b5f551c272b53d2f2fcdacd8cc1705245ec9a5cf8d53ca1cfc9bb" } } ], "extra": [ 1, 97, 21, 93, 138, 122, 40, 53, 6, 108, 177, 207, 63, 15, 232, 253, 145, 144, 55, 101, 59, 132, 47, 235, 247, 151, 126, 55, 116, 226, 57, 204, 54, 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