Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f67403bda7e4fedeed2a7922a7bd0f4f5dfc00953f5ff0de66482b11db692a0

Tx prefix hash: 536ae814fb303530a7785d1d706d9ebcb27dfc593277319adfdc6cc3031be549
Tx public key: d0a69ac2eab2f0755cd1fb5458b8a031c67450bfc864f8e990ab4b9c8c6fd1a6
Timestamp: 1699056839 Timestamp [UCT]: 2023-11-04 00:13:59 Age [y:d:h:m:s]: 01:362:20:41:09
Block: 884132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518047 RingCT/type: yes/0
Extra: 01d0a69ac2eab2f0755cd1fb5458b8a031c67450bfc864f8e990ab4b9c8c6fd1a60211000000024b8f5122000000000000000000

1 output(s) for total of 0.721944264000 dcy

stealth address amount amount idx
00: 63d291c6da39538fa7b1b378c5270896bb86229ab32f1688f2a6e6437e50c2a2 0.721944264000 1339865 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": 884142, "vin": [ { "gen": { "height": 884132 } } ], "vout": [ { "amount": 721944264, "target": { "key": "63d291c6da39538fa7b1b378c5270896bb86229ab32f1688f2a6e6437e50c2a2" } } ], "extra": [ 1, 208, 166, 154, 194, 234, 178, 240, 117, 92, 209, 251, 84, 88, 184, 160, 49, 198, 116, 80, 191, 200, 100, 248, 233, 144, 171, 75, 156, 140, 111, 209, 166, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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