Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf5911a8a8bfc823f1f55fb2d37e979f7229b7f7b1c1a5099e4bd2543bef54a7

Tx prefix hash: fe34e1d19427c52b7d352eadc39f332ad5cb7c7732aac58b2cf463c8fe4a0567
Tx public key: 1f70852a014bc89c4b49e8e38b5b94d643c3d78dfe7c5b743b627e57fb59c850
Timestamp: 1722167532 Timestamp [UCT]: 2024-07-28 11:52:12 Age [y:d:h:m:s]: 00:272:06:13:08
Block: 1075517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194525 RingCT/type: yes/0
Extra: 011f70852a014bc89c4b49e8e38b5b94d643c3d78dfe7c5b743b627e57fb59c85002110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c2e6ad74d007a843bb991056c980f2f600e5586c913e700542477a7872875b1 0.600000000000 1548046 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": 1075527, "vin": [ { "gen": { "height": 1075517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c2e6ad74d007a843bb991056c980f2f600e5586c913e700542477a7872875b1" } } ], "extra": [ 1, 31, 112, 133, 42, 1, 75, 200, 156, 75, 73, 232, 227, 139, 91, 148, 214, 67, 195, 215, 141, 254, 124, 91, 116, 59, 98, 126, 87, 251, 89, 200, 80, 2, 17, 0, 0, 0, 16, 145, 225, 60, 4, 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