Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a04cf41f7d94b2f058e28e56df485cb14f2ab7bc38298956ab43d4d3208a092d

Tx prefix hash: 6c459736fece37abd510d1364df11ef63ce1e27f524a144b4e08c38c01acea24
Tx public key: 66db0d6141c13e75b742d582016e0324d35909c021c4d333c008094ac432cd0b
Timestamp: 1735558960 Timestamp [UCT]: 2024-12-30 11:42:40 Age [y:d:h:m:s]: 00:324:08:54:17
Block: 1186412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229354 RingCT/type: yes/0
Extra: 0166db0d6141c13e75b742d582016e0324d35909c021c4d333c008094ac432cd0b02110000000d007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d178cf9c10097cb5e6fd95883eb3e9cbbb87cb76c10df779c9d9e6cec83e98e 0.600000000000 1672893 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": 1186422, "vin": [ { "gen": { "height": 1186412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d178cf9c10097cb5e6fd95883eb3e9cbbb87cb76c10df779c9d9e6cec83e98e" } } ], "extra": [ 1, 102, 219, 13, 97, 65, 193, 62, 117, 183, 66, 213, 130, 1, 110, 3, 36, 211, 89, 9, 192, 33, 196, 211, 51, 192, 8, 9, 74, 196, 50, 205, 11, 2, 17, 0, 0, 0, 13, 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