Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9feab95b9505e43c4fa2c221291bb99bd0b832b9a8fe0cefde43e6b80980624e

Tx prefix hash: 3ba2a5a0a90b38162462cf14560f31c8523f7f591ddd346d1130442026b28c88
Tx public key: 39fdec41f619cb2cbf178d4ea76c94e889724c1c592a0415526294b5d9bfa1c2
Timestamp: 1702890821 Timestamp [UCT]: 2023-12-18 09:13:41 Age [y:d:h:m:s]: 01:115:14:51:29
Block: 915712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343769 RingCT/type: yes/0
Extra: 0139fdec41f619cb2cbf178d4ea76c94e889724c1c592a0415526294b5d9bfa1c202110000000633af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 373b983922237de781835e0d56f04caa27a9f83306c3cd159f321d63b4064fca 0.600000000000 1373136 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": 915722, "vin": [ { "gen": { "height": 915712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "373b983922237de781835e0d56f04caa27a9f83306c3cd159f321d63b4064fca" } } ], "extra": [ 1, 57, 253, 236, 65, 246, 25, 203, 44, 191, 23, 141, 78, 167, 108, 148, 232, 137, 114, 76, 28, 89, 42, 4, 21, 82, 98, 148, 181, 217, 191, 161, 194, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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