Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d439336df7d53140c594ad7bbda7a7ee59b9d81f1322a4ba4c7153e3684353d

Tx prefix hash: 4afed0943c91401b004557a3bc00e7642e779ec5a2f5e3a119398bc6d2690721
Tx public key: e3f973ac8cfc06f28510e0ba44e8bfeca20837d8d3fb6bb0ca89e0c0bcf02bd4
Timestamp: 1698455652 Timestamp [UCT]: 2023-10-28 01:14:12 Age [y:d:h:m:s]: 01:346:07:18:05
Block: 879156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506166 RingCT/type: yes/0
Extra: 01e3f973ac8cfc06f28510e0ba44e8bfeca20837d8d3fb6bb0ca89e0c0bcf02bd4021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.749879068000 dcy

stealth address amount amount idx
00: 0dcc963de4cd9bc69ecc344f2fb92dcb92b420a7e0d909326f6e69f4266c68cb 0.749879068000 1334658 of 0

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": 879166, "vin": [ { "gen": { "height": 879156 } } ], "vout": [ { "amount": 749879068, "target": { "key": "0dcc963de4cd9bc69ecc344f2fb92dcb92b420a7e0d909326f6e69f4266c68cb" } } ], "extra": [ 1, 227, 249, 115, 172, 140, 252, 6, 242, 133, 16, 224, 186, 68, 232, 191, 236, 162, 8, 55, 216, 211, 251, 107, 176, 202, 137, 224, 192, 188, 240, 43, 212, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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