Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a1559f8acf1819da018c7e6737ca9df139e223055cc41f93c815f04e2556390

Tx prefix hash: e41fda99cafbd0dfdeef5c2f3dbf21a8f307f18b240e081afdddc69fb41e8036
Tx public key: 7055fc5e996968f533044842d919bd414ae843ca422ae18e05e4374eae67a3d4
Timestamp: 1694985312 Timestamp [UCT]: 2023-09-17 21:15:12 Age [y:d:h:m:s]: 02:022:16:00:12
Block: 850356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 535828 RingCT/type: yes/0
Extra: 017055fc5e996968f533044842d919bd414ae843ca422ae18e05e4374eae67a3d40211000000074b8f5122000000000000000000

1 output(s) for total of 0.934152173000 dcy

stealth address amount amount idx
00: 8bc2751ba2b740b282fe3d56666f7201812a8d40dd8427978025501680270825 0.934152173000 1304070 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": 850366, "vin": [ { "gen": { "height": 850356 } } ], "vout": [ { "amount": 934152173, "target": { "key": "8bc2751ba2b740b282fe3d56666f7201812a8d40dd8427978025501680270825" } } ], "extra": [ 1, 112, 85, 252, 94, 153, 105, 104, 245, 51, 4, 72, 66, 217, 25, 189, 65, 74, 232, 67, 202, 66, 42, 225, 142, 5, 228, 55, 78, 174, 103, 163, 212, 2, 17, 0, 0, 0, 7, 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