Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5cee2c998888dd689a05bd1f7f5bad17f59d2fd9583aee4edc602647aae129c

Tx prefix hash: 5fe1f537346eb5c0cbf7310d8f2dc994afbe8674d6be213b0d811b665d0f7c0b
Tx public key: 041851a6aa82c20872ece4122eb3f81fd3405364b4cf074ab3d28b960f99eb4f
Timestamp: 1734885657 Timestamp [UCT]: 2024-12-22 16:40:57 Age [y:d:h:m:s]: 00:093:19:32:59
Block: 1180874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66791 RingCT/type: yes/0
Extra: 01041851a6aa82c20872ece4122eb3f81fd3405364b4cf074ab3d28b960f99eb4f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6599afa86df009dc92559dbf16dea0977c024904ba2e2aeae503ab00f24bb234 0.600000000000 1667289 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": 1180884, "vin": [ { "gen": { "height": 1180874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6599afa86df009dc92559dbf16dea0977c024904ba2e2aeae503ab00f24bb234" } } ], "extra": [ 1, 4, 24, 81, 166, 170, 130, 194, 8, 114, 236, 228, 18, 46, 179, 248, 31, 211, 64, 83, 100, 180, 207, 7, 74, 179, 210, 139, 150, 15, 153, 235, 79, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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