Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4553e89e7273964435d3f8b54c47256e0ca11d7ebee0e65ace6ef5a529556537

Tx prefix hash: a400da69f2d4adc5500397f3cc5b2d62cfd49e4863e9f8d84c0e92b3ac51d6a9
Tx public key: 97aa418c39bf350f063dc299366e90a542135d85d78aec8f8001165487d98bd5
Timestamp: 1693267923 Timestamp [UCT]: 2023-08-29 00:12:03 Age [y:d:h:m:s]: 01:233:08:26:57
Block: 836107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427919 RingCT/type: yes/0
Extra: 0197aa418c39bf350f063dc299366e90a542135d85d78aec8f8001165487d98bd502110000000527f2911c000000000000000000

1 output(s) for total of 1.041431001000 dcy

stealth address amount amount idx
00: a2f4ff5a47e7c936aa40a72bb56d7ca9e35101cf4571d3f2e4898d27b003f178 1.041431001000 1288683 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": 836117, "vin": [ { "gen": { "height": 836107 } } ], "vout": [ { "amount": 1041431001, "target": { "key": "a2f4ff5a47e7c936aa40a72bb56d7ca9e35101cf4571d3f2e4898d27b003f178" } } ], "extra": [ 1, 151, 170, 65, 140, 57, 191, 53, 15, 6, 61, 194, 153, 54, 110, 144, 165, 66, 19, 93, 133, 215, 138, 236, 143, 128, 1, 22, 84, 135, 217, 139, 213, 2, 17, 0, 0, 0, 5, 39, 242, 145, 28, 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