Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94bacad94c906050bc149e2e2b1ce82e88dd2a3b81ea3dfd145792d67c6cbc01

Tx prefix hash: 683abff259e21adcb4aa698558c2a0db44e4cac40c9c8493b52736ef88415aa7
Tx public key: 528b75babc2f50209878950a07598c496a4b3641aaa8aae62e748e414c56ce7d
Timestamp: 1733545985 Timestamp [UCT]: 2024-12-07 04:33:05 Age [y:d:h:m:s]: 00:111:22:14:37
Block: 1169751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79788 RingCT/type: yes/0
Extra: 01528b75babc2f50209878950a07598c496a4b3641aaa8aae62e748e414c56ce7d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e855265f4c0110e8a1c4fdd1b374d2923f5fff307bfa2aeeacc585eb8551593 0.600000000000 1655474 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": 1169761, "vin": [ { "gen": { "height": 1169751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e855265f4c0110e8a1c4fdd1b374d2923f5fff307bfa2aeeacc585eb8551593" } } ], "extra": [ 1, 82, 139, 117, 186, 188, 47, 80, 32, 152, 120, 149, 10, 7, 89, 140, 73, 106, 75, 54, 65, 170, 168, 170, 230, 46, 116, 142, 65, 76, 86, 206, 125, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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