Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e99724a5802d9c4a40d26f49824a6c4a3b0d6e95fd4448dac8747b364a45d76

Tx prefix hash: af80af14893d9777e07e30c583cf0eb21808aea0c77a905bc55e33269d4108ff
Tx public key: 4320fa61d730e7d4f9d7228f6b54f833a5af2aab44468ef5bed0718090033711
Timestamp: 1672520177 Timestamp [UCT]: 2022-12-31 20:56:17 Age [y:d:h:m:s]: 01:336:21:55:25
Block: 664785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501823 RingCT/type: yes/0
Extra: 014320fa61d730e7d4f9d7228f6b54f833a5af2aab44468ef5bed071809003371102110000000152542ceb000000000000000000

1 output(s) for total of 3.848498260000 dcy

stealth address amount amount idx
00: a7f20aea1ba35c6a7b9765302218f1e6ca13f862d41ab2363b9a9684130e17f5 3.848498260000 1105794 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": 664795, "vin": [ { "gen": { "height": 664785 } } ], "vout": [ { "amount": 3848498260, "target": { "key": "a7f20aea1ba35c6a7b9765302218f1e6ca13f862d41ab2363b9a9684130e17f5" } } ], "extra": [ 1, 67, 32, 250, 97, 215, 48, 231, 212, 249, 215, 34, 143, 107, 84, 248, 51, 165, 175, 42, 171, 68, 70, 142, 245, 190, 208, 113, 128, 144, 3, 55, 17, 2, 17, 0, 0, 0, 1, 82, 84, 44, 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