Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05d8461d9ab0b3ff65af4cf1453cfb66632f89cf959122b70e3369637d37a7bd

Tx prefix hash: 19cfbdcfbb47a0ffcf98d1e2e0f6c0242353d73d1d01f4af7eaf741a8f3d3102
Tx public key: 2b79d82f2af75d098daf8e609e89e7581b94a1954e527605e4b2bbcd642738ad
Timestamp: 1716602783 Timestamp [UCT]: 2024-05-25 02:06:23 Age [y:d:h:m:s]: 00:159:11:28:25
Block: 1029398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114157 RingCT/type: yes/0
Extra: 012b79d82f2af75d098daf8e609e89e7581b94a1954e527605e4b2bbcd642738ad0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf277ca86d62769a7bd8574803d41d37fa5e1bc907b6f2949a25aea91a231568 0.600000000000 1497477 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": 1029408, "vin": [ { "gen": { "height": 1029398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf277ca86d62769a7bd8574803d41d37fa5e1bc907b6f2949a25aea91a231568" } } ], "extra": [ 1, 43, 121, 216, 47, 42, 247, 93, 9, 141, 175, 142, 96, 158, 137, 231, 88, 27, 148, 161, 149, 78, 82, 118, 5, 228, 178, 187, 205, 100, 39, 56, 173, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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