Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8ac3f723aff4f0b3c5347d8dc8a94eba5fd45065f48a95584551f01ddd8dada

Tx prefix hash: 92312b38da2e17b4e0de2cb1a0ddcd7599128e0ce0e61dd26667fb3627ae21b9
Tx public key: f3d4027af556a37191973ae3c8d8d809d397467fab08b11d7e6a77d4b3c15fbd
Timestamp: 1697409775 Timestamp [UCT]: 2023-10-15 22:42:55 Age [y:d:h:m:s]: 01:175:12:47:21
Block: 870474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386477 RingCT/type: yes/0
Extra: 01f3d4027af556a37191973ae3c8d8d809d397467fab08b11d7e6a77d4b3c15fbd02110000000a33af99f4000000000000000000

1 output(s) for total of 0.801232051000 dcy

stealth address amount amount idx
00: db65159d3b5e55c8ee7cab7c923e1c6ff6292cc64375f0171e91533da415c210 0.801232051000 1325353 of 0

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": 870484, "vin": [ { "gen": { "height": 870474 } } ], "vout": [ { "amount": 801232051, "target": { "key": "db65159d3b5e55c8ee7cab7c923e1c6ff6292cc64375f0171e91533da415c210" } } ], "extra": [ 1, 243, 212, 2, 122, 245, 86, 163, 113, 145, 151, 58, 227, 200, 216, 216, 9, 211, 151, 70, 127, 171, 8, 177, 29, 126, 106, 119, 212, 179, 193, 95, 189, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 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