Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd1827a06334a78a4782748916cbf7fe6fb1f962c0d2d578b5414abfb5c00445

Tx prefix hash: 23cb8301f824890d82b1795d91b63a5850ed2e4e750f33bfd46746add983742c
Tx public key: e0a94d00e4ab57da3f105d725fd2be96fd27b3c64d07f12f023931fd2145dd62
Timestamp: 1707289184 Timestamp [UCT]: 2024-02-07 06:59:44 Age [y:d:h:m:s]: 01:071:07:42:54
Block: 952173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312035 RingCT/type: yes/0
Extra: 01e0a94d00e4ab57da3f105d725fd2be96fd27b3c64d07f12f023931fd2145dd6202110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47bb2309a3fd3190354618a655a34e417930dbee92b26593815b959092b3afc5 0.600000000000 1411055 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": 952183, "vin": [ { "gen": { "height": 952173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47bb2309a3fd3190354618a655a34e417930dbee92b26593815b959092b3afc5" } } ], "extra": [ 1, 224, 169, 77, 0, 228, 171, 87, 218, 63, 16, 93, 114, 95, 210, 190, 150, 253, 39, 179, 198, 77, 7, 241, 47, 2, 57, 49, 253, 33, 69, 221, 98, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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