Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b109a97bdb717d6bd48905de0b9b63e58213fc06d084f57360a632a922a2806

Tx prefix hash: 9ba12fe59668c195fb681fd13000480b86cc1f728af19e86818a363430047448
Tx public key: ffb30cff4aaec2ca09082870a8d8cad4db0b4a744399f6e1bcc86467da2b06a5
Timestamp: 1709834438 Timestamp [UCT]: 2024-03-07 18:00:38 Age [y:d:h:m:s]: 01:259:23:43:40
Block: 973290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444529 RingCT/type: yes/0
Extra: 01ffb30cff4aaec2ca09082870a8d8cad4db0b4a744399f6e1bcc86467da2b06a502110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d55cd6f363bf5bce1c49a4c7f553e40cb34eade17a0a8d6a427955e547d442d6 0.600000000000 1433225 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": 973300, "vin": [ { "gen": { "height": 973290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d55cd6f363bf5bce1c49a4c7f553e40cb34eade17a0a8d6a427955e547d442d6" } } ], "extra": [ 1, 255, 179, 12, 255, 74, 174, 194, 202, 9, 8, 40, 112, 168, 216, 202, 212, 219, 11, 74, 116, 67, 153, 246, 225, 188, 200, 100, 103, 218, 43, 6, 165, 2, 17, 0, 0, 0, 13, 122, 156, 244, 199, 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