Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 301c3097c601b4f959039cdeddc0feb79d0981f4b22b6e1b1203e08384a3cc9d

Tx prefix hash: fc4baf96ee54288f79615ebbf3a6986bb2f7405cd373d3f849c79a6737cf0fa4
Tx public key: 8e4d210740a14d3f3eb6a96d7a43f17bede06ecc8a687f0da46a79a4ebc75a2c
Timestamp: 1664336026 Timestamp [UCT]: 2022-09-28 03:33:46 Age [y:d:h:m:s]: 02:173:07:00:50
Block: 597281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645365 RingCT/type: yes/0
Extra: 018e4d210740a14d3f3eb6a96d7a43f17bede06ecc8a687f0da46a79a4ebc75a2c021100000001dedc788d000000000000000000

1 output(s) for total of 6.441101867000 dcy

stealth address amount amount idx
00: aee5f9df9e0bdb4f6dd46f934fcf24c44f332c5fd685f5a1cb2a5589e7ce2c2a 6.441101867000 1032660 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": 597291, "vin": [ { "gen": { "height": 597281 } } ], "vout": [ { "amount": 6441101867, "target": { "key": "aee5f9df9e0bdb4f6dd46f934fcf24c44f332c5fd685f5a1cb2a5589e7ce2c2a" } } ], "extra": [ 1, 142, 77, 33, 7, 64, 161, 77, 63, 62, 182, 169, 109, 122, 67, 241, 123, 237, 224, 110, 204, 138, 104, 127, 13, 164, 106, 121, 164, 235, 199, 90, 44, 2, 17, 0, 0, 0, 1, 222, 220, 120, 141, 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