Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d44b8a95fddb2d6ca8b17ee38938444a35485b99c5a27dee0850af088514044

Tx prefix hash: a0aa9927afc9397a0b3093a6d3841f0f514422f52bbb49a749f42cc2cc5faf8e
Tx public key: be9b731f2bc1a62eee722a242b7c71dd19c711fd8523e7a788cd1f7c36603ce6
Timestamp: 1637253386 Timestamp [UCT]: 2021-11-18 16:36:26 Age [y:d:h:m:s]: 03:048:09:39:57
Block: 377090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 813350 RingCT/type: yes/0
Extra: 01be9b731f2bc1a62eee722a242b7c71dd19c711fd8523e7a788cd1f7c36603ce6021100000018b494d89c000000000000000000

1 output(s) for total of 34.557687853000 dcy

stealth address amount amount idx
00: dcf7e0e3e44b724c9f82573b19d60e5c8765e56df2f9f7293c877f7ce6b5789a 34.557687853000 762772 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": 377100, "vin": [ { "gen": { "height": 377090 } } ], "vout": [ { "amount": 34557687853, "target": { "key": "dcf7e0e3e44b724c9f82573b19d60e5c8765e56df2f9f7293c877f7ce6b5789a" } } ], "extra": [ 1, 190, 155, 115, 31, 43, 193, 166, 46, 238, 114, 42, 36, 43, 124, 113, 221, 25, 199, 17, 253, 133, 35, 231, 167, 136, 205, 31, 124, 54, 96, 60, 230, 2, 17, 0, 0, 0, 24, 180, 148, 216, 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