Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4e8b11c968caf695c37c7eb2649220b28424cf09891643c66f76848bc72a2fd

Tx prefix hash: 9e013c42912b504c674dc4e1add48595b2f726e5505d2c694b122d1977e95142
Tx public key: 15254125676cfe881a1ea3d9414dc3e441ae58d4bc42b0ed2fb2e423574915ed
Timestamp: 1749725115 Timestamp [UCT]: 2025-06-12 10:45:15 Age [y:d:h:m:s]: 00:149:18:52:17
Block: 1303393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104767 RingCT/type: yes/0
Extra: 0115254125676cfe881a1ea3d9414dc3e441ae58d4bc42b0ed2fb2e423574915ed021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc6394f998832508f8e156dbcb6cf90b527bc2970c4b00450975bbf3b7a83edd 0.600000000000 1790972 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": 1303403, "vin": [ { "gen": { "height": 1303393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc6394f998832508f8e156dbcb6cf90b527bc2970c4b00450975bbf3b7a83edd" } } ], "extra": [ 1, 21, 37, 65, 37, 103, 108, 254, 136, 26, 30, 163, 217, 65, 77, 195, 228, 65, 174, 88, 212, 188, 66, 176, 237, 47, 178, 228, 35, 87, 73, 21, 237, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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