Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2bd88f056575ec5d780d3315991482094ce0befb9dfa7c39857e0adb4ca8310

Tx prefix hash: d269a71862fc38bd4ab241cbce658e40e715e329458c81e0a1f215a407c24016
Tx public key: a1b5280ff09f0e69eea7ee9f5d289f2b3d77ef0d7fa288c899a15e27fc6e83ef
Timestamp: 1717283965 Timestamp [UCT]: 2024-06-01 23:19:25 Age [y:d:h:m:s]: 00:302:12:42:20
Block: 1035047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216205 RingCT/type: yes/0
Extra: 01a1b5280ff09f0e69eea7ee9f5d289f2b3d77ef0d7fa288c899a15e27fc6e83ef02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 439fde449c6c42d1a03709d2b58a094c966ec127c21b957673b70b557f025fa7 0.600000000000 1503566 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": 1035057, "vin": [ { "gen": { "height": 1035047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "439fde449c6c42d1a03709d2b58a094c966ec127c21b957673b70b557f025fa7" } } ], "extra": [ 1, 161, 181, 40, 15, 240, 159, 14, 105, 238, 167, 238, 159, 93, 40, 159, 43, 61, 119, 239, 13, 127, 162, 136, 200, 153, 161, 94, 39, 252, 110, 131, 239, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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