Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b553aa3b7cdf3613a20dd2b38f5ce143be7ec918f92b1f455e1998c277e523fa

Tx prefix hash: bf5b2079d75fa2dffe7ed601ee4f9fb7c8693ad7b51c7d3c7b958252710ddc6e
Tx public key: a8e01ec0b2a279029f61969d687ead7b738aaba7fe001557181c2b92aa214c56
Timestamp: 1738612125 Timestamp [UCT]: 2025-02-03 19:48:45 Age [y:d:h:m:s]: 00:288:07:07:18
Block: 1211421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203816 RingCT/type: yes/0
Extra: 01a8e01ec0b2a279029f61969d687ead7b738aaba7fe001557181c2b92aa214c560211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0531f261285662f070f666c0080fd0dc87e448f45336186a2a76b685a97ff87 0.600000000000 1698182 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": 1211431, "vin": [ { "gen": { "height": 1211421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0531f261285662f070f666c0080fd0dc87e448f45336186a2a76b685a97ff87" } } ], "extra": [ 1, 168, 224, 30, 192, 178, 162, 121, 2, 159, 97, 150, 157, 104, 126, 173, 123, 115, 138, 171, 167, 254, 0, 21, 87, 24, 28, 43, 146, 170, 33, 76, 86, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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