Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dbf9478b0c19c730803df955717d9f9eae009794e64241e30492a0e5ecb7727

Tx prefix hash: 766752f2680fdd78eadc7869df6f87e171a54341f4e2e7af3016f27e14bd2d69
Tx public key: ca15fab3bcbe0bee8e2bc4a9f9fd230fa181260178c4a01297879afa35b8d5cf
Timestamp: 1706346634 Timestamp [UCT]: 2024-01-27 09:10:34 Age [y:d:h:m:s]: 01:073:02:40:26
Block: 944339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313349 RingCT/type: yes/0
Extra: 01ca15fab3bcbe0bee8e2bc4a9f9fd230fa181260178c4a01297879afa35b8d5cf0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24f4f76e0a14280a2b0785804424efce14b584a1990a10ddf8a4ea13f45be60f 0.600000000000 1402575 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": 944349, "vin": [ { "gen": { "height": 944339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24f4f76e0a14280a2b0785804424efce14b584a1990a10ddf8a4ea13f45be60f" } } ], "extra": [ 1, 202, 21, 250, 179, 188, 190, 11, 238, 142, 43, 196, 169, 249, 253, 35, 15, 161, 129, 38, 1, 120, 196, 160, 18, 151, 135, 154, 250, 53, 184, 213, 207, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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