Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 072bd4c45768fa49553a7baf3a9c862101e57f6b895cd4d65ab40e4b6739371c

Tx prefix hash: 9966543b717c95b32beeef2f5c1cd19d3efc08af4b47d220c43461f9b62c5892
Tx public key: 595b280894f92405a24e489af406cfcb5f24380edbf20a8420d93f03145d4d0d
Timestamp: 1714322667 Timestamp [UCT]: 2024-04-28 16:44:27 Age [y:d:h:m:s]: 00:271:08:40:27
Block: 1010480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194191 RingCT/type: yes/0
Extra: 01595b280894f92405a24e489af406cfcb5f24380edbf20a8420d93f03145d4d0d02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f79e28c612c84abf1e6b670f6ab0b5c271b309e6988e4aefb11adb4405fefd81 0.600000000000 1472450 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": 1010490, "vin": [ { "gen": { "height": 1010480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f79e28c612c84abf1e6b670f6ab0b5c271b309e6988e4aefb11adb4405fefd81" } } ], "extra": [ 1, 89, 91, 40, 8, 148, 249, 36, 5, 162, 78, 72, 154, 244, 6, 207, 203, 95, 36, 56, 14, 219, 242, 10, 132, 32, 217, 63, 3, 20, 93, 77, 13, 2, 17, 0, 0, 0, 2, 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