Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d062d06f27a2d10e9c85169d7a4da2b40f288e468ce55d5b424000fb605fdd44

Tx prefix hash: 501a2134cbceb0a07cc8a5aee7a13d039c27d172d334baac6d6811cd237cf3f7
Tx public key: 4b3f1670feeca9576c3d3c4e74ccb13ca708c57d45c129326cdf97bfad0880d5
Timestamp: 1699583603 Timestamp [UCT]: 2023-11-10 02:33:23 Age [y:d:h:m:s]: 01:187:22:02:48
Block: 888298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395515 RingCT/type: yes/0
Extra: 014b3f1670feeca9576c3d3c4e74ccb13ca708c57d45c129326cdf97bfad0880d502110000000433af99f4000000000000000000

1 output(s) for total of 0.699358691000 dcy

stealth address amount amount idx
00: f435395662adbc86ad13cd9ad7601dd78285cf4778a9b0a32ea4028f37fb23aa 0.699358691000 1344237 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": 888308, "vin": [ { "gen": { "height": 888298 } } ], "vout": [ { "amount": 699358691, "target": { "key": "f435395662adbc86ad13cd9ad7601dd78285cf4778a9b0a32ea4028f37fb23aa" } } ], "extra": [ 1, 75, 63, 22, 112, 254, 236, 169, 87, 108, 61, 60, 78, 116, 204, 177, 60, 167, 8, 197, 125, 69, 193, 41, 50, 108, 223, 151, 191, 173, 8, 128, 213, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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