Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fdda04e6912d27de2e0e5e4c7ff1b8bdc0a48856acf5586128fc1b19204f777

Tx prefix hash: 5aaade63ed82a8cde06a761a55c1583c793a3b2d5b2e79e8a56f67279c31932d
Tx public key: 338cdba6e870aa93b07e26a6d05403e21f478f11331b8535817a5694622f3225
Timestamp: 1727515318 Timestamp [UCT]: 2024-09-28 09:21:58 Age [y:d:h:m:s]: 00:104:09:15:49
Block: 1119871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74623 RingCT/type: yes/0
Extra: 01338cdba6e870aa93b07e26a6d05403e21f478f11331b8535817a5694622f322502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16d08ddd0c7bcf1be2c3c4b2c0ced074fd176d0ad9891109bb5756e33211fb68 0.600000000000 1601582 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": 1119881, "vin": [ { "gen": { "height": 1119871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16d08ddd0c7bcf1be2c3c4b2c0ced074fd176d0ad9891109bb5756e33211fb68" } } ], "extra": [ 1, 51, 140, 219, 166, 232, 112, 170, 147, 176, 126, 38, 166, 208, 84, 3, 226, 31, 71, 143, 17, 51, 27, 133, 53, 129, 122, 86, 148, 98, 47, 50, 37, 2, 17, 0, 0, 0, 5, 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