Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae1cf9f6488161eaac6c3ab4c75328a3ad64cdb634ea1718db0e243f26941a5e

Tx prefix hash: 193d6ff62e8368b19c390b1b32a4c525887a721c501c566b8678215073393a5a
Tx public key: f494ce32f28e311fe244e82077938d457f517df41ddd1e0c20dfe43ba10c46ba
Timestamp: 1726564614 Timestamp [UCT]: 2024-09-17 09:16:54 Age [y:d:h:m:s]: 00:068:17:36:57
Block: 1111972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49147 RingCT/type: yes/0
Extra: 01f494ce32f28e311fe244e82077938d457f517df41ddd1e0c20dfe43ba10c46ba02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e377a87ae8c06c8c8fcce0d86181502e46639477bf65a029faae3cdd602dbfd4 0.600000000000 1591125 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": 1111982, "vin": [ { "gen": { "height": 1111972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e377a87ae8c06c8c8fcce0d86181502e46639477bf65a029faae3cdd602dbfd4" } } ], "extra": [ 1, 244, 148, 206, 50, 242, 142, 49, 31, 226, 68, 232, 32, 119, 147, 141, 69, 127, 81, 125, 244, 29, 221, 30, 12, 32, 223, 228, 59, 161, 12, 70, 186, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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