Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7280541614b6266f3b5519caa800d14fcbdcf81d3aa65c824a6f2daa3fff76b

Tx prefix hash: 47f908396503da491dfb9601f77db91da791153ad26d58eedfcab7451463e644
Tx public key: 02e86f914f4fa39fba876fe51fd4cfa4acc7e59793c7c4d1df96bdc9eaf1323a
Timestamp: 1734834470 Timestamp [UCT]: 2024-12-22 02:27:50 Age [y:d:h:m:s]: 01:001:15:29:54
Block: 1180455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259575 RingCT/type: yes/0
Extra: 0102e86f914f4fa39fba876fe51fd4cfa4acc7e59793c7c4d1df96bdc9eaf1323a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1336aa697b37d18bb69058bc02e61e71bf86a704436c19c10f060a7db22e3f1 0.600000000000 1666866 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": 1180465, "vin": [ { "gen": { "height": 1180455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1336aa697b37d18bb69058bc02e61e71bf86a704436c19c10f060a7db22e3f1" } } ], "extra": [ 1, 2, 232, 111, 145, 79, 79, 163, 159, 186, 135, 111, 229, 31, 212, 207, 164, 172, 199, 229, 151, 147, 199, 196, 209, 223, 150, 189, 201, 234, 241, 50, 58, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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