Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 044d3af8cfe3dd2e1733338189063b93275d16d5bdcad537f620371c74155565

Tx prefix hash: cba1a2a91bf953f7adade95b7baa070febf39eab98ed39804f59425fe03f149b
Tx public key: 7a1cd612cfa1560308d66c97567c5e06d87d70f9f81b549aa15cde6450d60a9c
Timestamp: 1685792884 Timestamp [UCT]: 2023-06-03 11:48:04 Age [y:d:h:m:s]: 02:015:22:52:50
Block: 774204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 533388 RingCT/type: yes/0
Extra: 017a1cd612cfa1560308d66c97567c5e06d87d70f9f81b549aa15cde6450d60a9c021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.670094048000 dcy

stealth address amount amount idx
00: 9f5471e536d2fd638ea14587a9fb506e0bfdc1dafe6816606856464924c4d7fa 1.670094048000 1223671 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": 774214, "vin": [ { "gen": { "height": 774204 } } ], "vout": [ { "amount": 1670094048, "target": { "key": "9f5471e536d2fd638ea14587a9fb506e0bfdc1dafe6816606856464924c4d7fa" } } ], "extra": [ 1, 122, 28, 214, 18, 207, 161, 86, 3, 8, 214, 108, 151, 86, 124, 94, 6, 216, 125, 112, 249, 248, 27, 84, 154, 161, 92, 222, 100, 80, 214, 10, 156, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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