Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da98ced34bc10f6f575f22d0edf402a7650d2ed9db52c45fbe0dd301c3ef5965

Tx prefix hash: ea6e152f66031e4fbe4a8c46e000d06a14d45c77c5e8b36703cb799f05d784b9
Tx public key: a390c99f1b50bc9903a0f82d1d1546394dc451f386474fccead1dc87b563ec47
Timestamp: 1723044459 Timestamp [UCT]: 2024-08-07 15:27:39 Age [y:d:h:m:s]: 00:199:16:52:18
Block: 1082791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142578 RingCT/type: yes/0
Extra: 01a390c99f1b50bc9903a0f82d1d1546394dc451f386474fccead1dc87b563ec4702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac763a4ff80667b598194ea4efd61d53f88e7a6e97932ff42ba5a9f20560e9e6 0.600000000000 1556622 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": 1082801, "vin": [ { "gen": { "height": 1082791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac763a4ff80667b598194ea4efd61d53f88e7a6e97932ff42ba5a9f20560e9e6" } } ], "extra": [ 1, 163, 144, 201, 159, 27, 80, 188, 153, 3, 160, 248, 45, 29, 21, 70, 57, 77, 196, 81, 243, 134, 71, 79, 204, 234, 209, 220, 135, 181, 99, 236, 71, 2, 17, 0, 0, 0, 2, 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