Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2378d701aff55d163e703b5ec495d5b2a40fea7d71018f0f38eaa170677fb80e

Tx prefix hash: 3fbd6f937a942dd56102de8a880ce58be7983633350da981b0954a5ea1345fdf
Tx public key: 27d21c8caa2cec70cfd6cbb0423baa82f54efbbdbd2b36cbe1bc4c605442c72b
Timestamp: 1714337511 Timestamp [UCT]: 2024-04-28 20:51:51 Age [y:d:h:m:s]: 00:354:15:27:25
Block: 1010609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253530 RingCT/type: yes/0
Extra: 0127d21c8caa2cec70cfd6cbb0423baa82f54efbbdbd2b36cbe1bc4c605442c72b0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cffdf506ce5312a7e4abdf557fd77aa8cfcb261218859ec3a0bfa550069f4e6b 0.600000000000 1472611 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": 1010619, "vin": [ { "gen": { "height": 1010609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cffdf506ce5312a7e4abdf557fd77aa8cfcb261218859ec3a0bfa550069f4e6b" } } ], "extra": [ 1, 39, 210, 28, 140, 170, 44, 236, 112, 207, 214, 203, 176, 66, 59, 170, 130, 245, 78, 251, 189, 189, 43, 54, 203, 225, 188, 76, 96, 84, 66, 199, 43, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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