Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cec89c2fd93efcf39084152da05a2fda0a2bdce63c8d6c7c51e8d7d10a9e059f

Tx prefix hash: ba0bc63fab173a0de4582716fb2d7335b630be9241c9f91b5687515e2073cd4c
Tx public key: 4ea5c15cc71591453dc7ee0cb50efb3c72f45e64b9c5cd6e8339ed4608dda1df
Timestamp: 1712963879 Timestamp [UCT]: 2024-04-12 23:17:59 Age [y:d:h:m:s]: 01:039:20:15:40
Block: 999193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289491 RingCT/type: yes/0
Extra: 014ea5c15cc71591453dc7ee0cb50efb3c72f45e64b9c5cd6e8339ed4608dda1df02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1429234eae115605df4a6fa78decba7a8c3859f2d034ce5da741c2ac72cf6feb 0.600000000000 1459671 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": 999203, "vin": [ { "gen": { "height": 999193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1429234eae115605df4a6fa78decba7a8c3859f2d034ce5da741c2ac72cf6feb" } } ], "extra": [ 1, 78, 165, 193, 92, 199, 21, 145, 69, 61, 199, 238, 12, 181, 14, 251, 60, 114, 244, 94, 100, 185, 197, 205, 110, 131, 57, 237, 70, 8, 221, 161, 223, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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